Method for isochronous data transport over a wireless network

ABSTRACT

Method for isochronous data packet transport over a wireless network, comprising the steps of: collecting a plurality of isochronous data packets at a service specific convergence sublayer (SSCS) of a wireless source device; posting said plurality of isochronous data packets as a whole to a common part convergence sub-layer (CPCS) of the wireless source device, wherein said plurality of isochronous data packets posted to the common part convergence sub-layer corresponds to the amount of isochronous data packets generated by a transmitter over a 2 ms period.

[0001] The invention concerns a method for carrying out isochronous data transport over a wireless network.

[0002] The context of this invention is the transport of IEEE 1394 services in alternative interconnects (non 1394 based interconnects). This is particularly relevant in the case a wireless network is used to interconnect IEEE 1394 buses.

[0003] One example of wireless network is the BRAN HIPERLAN 2 (‘HL2’) network, which is being specified by ETSI. The HIPERLAN 2 IEEE 1394 Service Specific Convergence Sub-layer (SSCS) aims at providing the services of an IEEE 1394 Link layer. This allows providing an HL2 1394 link interface, and to put such an interface on IEEE 1394 devices. The Service Specific Convergence Sub-Layer passes data to the Common Part Convergence Sub-layer (CPCS) followed by the Segmentation and Reassembly (SAR) sublayer. The CPCS and SAR form the interface between the SSCS and the Data Link Control (DLC) layer.

[0004] On the other hand, the document IEC 61883 defines mechanisms to transport IEEE 1394 isochronous services. This document defines in particular how isochronous data packets, such as for example MPEG 2 Transport Stream data (source packets), are to be formatted for insertion into IEEE 1394 isochronous packets.

[0005] When MPEG2 (TS) data is sent in a IEEE 1394 isochronous stream, this data is, according to IEC 61883, segmented into several data blocks so that the bandwidth reservation mechanisms over the IEEE 1394 125 μs bus cycle remain efficient by sending some data blocks every cycle and thus avoiding bursts as much as possible. Each MPEG TS packet is segmented into eight data blocks. The segmentation is carried out in order to send data, if possible, every cycle, so as to avoid bursts.

[0006] Every 125 μs cycle, an isochronous packet dedicated to a given channel may contain zero, one, two or four data blocks. Each isochronous packet comprises IEEE 1394 packet header and payload Cyclic Redundancy Check (‘CRC’). In addition, when the isochronous packet contains at least one data block, a Common Isochronous Packet (‘CIP’) header of 8 bytes is inserted into the payload of the isochronous packet. The header, CRC and CIP represent 20 bytes of overhead data for every cycle during which data blocks are sent.

[0007] For the purpose of transport over the wireless link, it can be imagined that the HIPERLAN 2 SSCS layer of an interface device between a wired bus and the wireless link adds wireless time stamps to the IEEE 1394 isochronous packets and posts them to the Common Part Convergence Layer (CPCS). The CPCS packets are segmented into 48 byte blocks, which correspond to the Data Link Control (DLC) layer slots.

[0008] The amount of overhead data is not negligible compared to the amount of payload data, if IEEE 1394 isochronous packets, including the IEC 61883 CIP header and the wireless stamps are posted to the CPCS layer. An improved method for providing transmission of isochronous data over wireless links is desirable.

[0009] The object of the invention is method for isochronous data packet transport over a wireless network, comprising the steps of:

[0010] collecting a plurality of isochronous data packets at a service specific convergence sublayer (SSCS) of a wireless source device;

[0011] posting said plurality of isochronous data packets as a whole to a common part convergence sub-layer (CPCS) of the wireless source device, wherein said plurality of isochronous data packets posted to the common part convergence sub-layer corresponds to the amount of isochronous data packets generated by a transmitter over a wireless frame period.

[0012] The inventors recognized that, since the 125 μs IEEE1394 cycle applies only to the wired IEEE 1394 bus, there is no need to take this constraint into account on the wireless link. In particular, it is more efficient to post a plurality of isochronous packets in a concatenated form to the CPCS layer.

[0013] Isochronous packets are either provided directly by an application, or received over an IEEE 1394/IEC 61883 bus.

[0014] Other characteristics and advantages of the invention shall appear through the description of a preferred embodiment, illustrated by the attached drawings among which:

[0015]FIG. 1 represents an example of a network comprising two wired busses and a wireless link between the busses,

[0016]FIG. 2 represents the protocol stack of an interface device of FIG. 2, i.e. a portal interfacing a wired bus with the wireless link,

[0017]FIG. 3 is a diagram of the encapsulation method according to the invention,

[0018]FIG. 4 is a diagram of an isochronous resource manager request packet format (prior art),

[0019]FIG. 5 is a diagram of an isochronous resource manager request packet format according to the embodiment,

[0020]FIG. 6 is a diagram of an information element used to select an encapsulation method according to the embodiment,

[0021]FIG. 7 is a diagram of an information element used during the association process of a device in order to inform a Central Controller as to its capacity to use an encapsulation method according to the embodiment.

[0022] The embodiment focuses on ETSI BRAN HIPERLAN 2 (“HL2”) as the wireless network technology, but the invention is not limited to this embodiment.

[0023] More information regarding IEEE 1394 can be obtained in the documents (a) IEEE Std 1394-1995 ‘standard for a High Performance Serial Bus and (b) IEEE Std 1394a-2000 ‘standard for a High Performance Serial Bus-Amendment 1’.

[0024] Transport of MPEG 2 type data over an IEEE 1394 bus is described by the document (c) IEC 61883-1 (1998-02) Consumer audio/video equipment-Digital interface-Parts 1 and 4.

[0025] According to the present embodiment, the wireless links are based on the ETSI BRAN Hiperlan 2 draft standard, and in particular on document (e) ‘Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Packet based convergence layer; Part 3: IEEE 1394 Service Specific Convergence Sublayer (SSCS), version 0.0.0 of December 1999, as well as on document (f) ‘Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Packet based convergence layer; Part 1: Common Part, version 0.g of November 1999.

[0026]FIG. 1 is a diagram of a network comprising two IEEE 1394 busses, respectively referenced 1 and 3. A number of IEEE 1394 devices are connected to each bus: devices 1A and 1B to bus 1 and device 3A to bus 3. Portals W1 and W3 are connected respectively to busses 1 and 3, and act as interfaces between the busses and the radio transmission medium. The network comprises further wireless device W2 and W4, which are not connected to an IEEE 1394 wired bus. For the purpose of the present embodiment, device W4 acts as the Central Controller (‘CC’) of the wireless part of the network. New devices on the wireless network register with the Central Controller. This phase is called ‘association’. Moreover, the Central Controller grants access to wireless network resources and sets up connections between devices of the wireless network. The functionalities of a Central Controller in a Hiperlan 2 network will not be described in more detail, as they are well known from the corresponding HIPERLAN 2 documentation available from ETSI.

[0027] In HIPERLAN 2, a time division multiple access/time division duplex (TDMA-TDD) scheme is used. The period of a medium access control (MAC) frame is of 2 ms. This is to be compared with the 125 μs cycle of the IEEE 1394 busses.

[0028]FIG. 2 represents the protocol stack of a wireless device (be it a portal or a stand-alone device) in a Hiperlan 2 wireless network. From bottom to top, the stack comprises a physical layer (‘PHY’), a data link control Layer (‘DLC’), a convergence layer (‘CL’), followed by higher layers. The convergence layer CL may be of several types, in particular of the cell based type or of the packet based type. The packet based convergence layer comprises a number of service specific convergence sub-layers (‘SSCS’). Examples of SSCS layers currently specified or under specification concern the Ethernet or the IEEE 1394 environment. Below this specific sublayer, a common part convergence sublayer (‘CPCS’) is included, followed by a segmentation and reassembly sublayer (‘SAR’).

[0029] The convergence layer prepares fixed-size packets (‘SAR-PDUs’) and forwards them to the data link control layer for transmission.

[0030] It is supposed in what follows that an lsochronous Resource Manager (IRM) is defined on the wireless network. Devices wishing to open an isochronous channel and a given bandwidth send requests to the IRM, which reserves the required resources or rejects the reservation request.

[0031] It is proposed to define a new isochronous data transport mode allowing native MPEG2 TS to be transported over a Hiperlan 2 link. This will consist in building a source packet (as described in IEC 61183), and send it as it is (without segmenting it into data blocks) over the radio link.

[0032] According to a variant embodiment, in order to remain close to IEEE 1394 and IEC 61883, the CIP overhead may be added to the entire source packet. The 1394 isochronous packet header and CRC may be added as well. Nevertheless, this is not the preferred solution: according to the present embodiment, neither CIP nor CRC are used.

[0033] At the receiving side, the source packet is buffered, based on the processing of its wireless time stamp, which was added by the SSCS layer of the transmitter. No reconstruction of the packet is needed, since it has not been segmented into data blocks. The receiver buffer size has to be adapted to the jitter (5 ms) over the wireless link.

[0034] The transport mode according to the invention may be an optional mode, as a choice among a number of possible transport modes. It may also be mandatory. Both cases as well as their impacts are described in this application.

[0035] If the inventive mode is optional, the SSCS layer of a device will indicate to the Central Controller's SSCS during the association whether it supports this mode or not.

[0036] An application of a device on the wireless link may ask to use the inventive MPEG2 transport mode or another isochronous packet mode (such as the mode described in the introduction, i.e. where the MPEG TS packets are segmented when it is reserving resources with an Isochronous Resource Manager of the wireless link, using for example a specific field in the lock command used for the reservation.

[0037] The Central Controller side will then generate a multicast DLC connection setup, and indicate in an Information Element (IE) in a convergence layer (‘CL’) container which kind of transport mode is to be used.

[0038] Each side of the multicast link knows after this what kind of transport mode is to be used.

[0039] According to the present embodiment, the following mode is used for direct MPEG2 over HL2 encapsulation.

[0040] The SSCS of the transmitter device appends a Time Stamp as specified by IEC 61883 part 4 to every MPEG2 TS packet of 188 bytes, in order to build a source packet of 192 bytes.

[0041] This source packet may be posted as it is to the CPCS for an already established DLC connection. According to a variant embodiment, it is even better that several MPEG2 source packets be collected together and posted as a whole to the CPCS.

[0042] As an improvement, a Cyclic Redundancy Check is added to protect any individual source packet. This CRC would be a SSCS specific overhead added to every source packet. Preferably, this CRC is based on the same polynomial as for the IEEE 1394-1995 isochronous packet payload.

[0043] According to document (f), packets constructed by the CPCS layer comprise a trailer of four bytes, two of which indicate the length of the payload. Source packets (and also CRC protected source packets) have a known fixed length—192 bytes for non-protected source packets—so that the CPCS length field can be used at the receiving side to recover individual MPEG2 source packets. Each CPCS SDU/PDU comprises an integer number of source packets.

[0044] For the sake of consistency with the output plug control register (‘oPCR’) Payload and Overhead ID fields, as described in a European patent application 00401324.9 filed on May 15, 2000 by the same applicant, having same inventors and entitled “Method for reserving isochronous resources in a wireless network”, a transmitter (also called source, or talker) shall generate one CPCS packet for every 2 ms period: several source packets are thus put together into one CPCS packet.

[0045] The output plug control register (‘oPCR’) of the transmitter shall reflect the maximum size of a CPCS packet for a 2 ms period.

[0046] The OPCR payload field of the transmitter shall reflect one of the two following types of information:

[0047] the maximum size of the CPCS packet (including source packet bytes, and the SSCSICPCS overhead (source packet CRC added by the SSCS, if it has been added, and the CPCS trailer and padding bytes)); or

[0048] the maximum size of the CPCS packet user data (i.e. the maximum number of sourced packet bytes that the transmitter may generate in a 2 ms period): the oPCR overhead ID field reflects the SSCS/CPCS overhead (source packet CRC, if available and the CPCS trailer and padding bytes).

[0049] The difference between the two alternatives is that the overhead is indicated in a separate field of the oPCR register in the second case.

[0050] A CPCS packet is not necessarily mapped into one frame: there is no obligation for a CPCS packet to be sent entirely within one HL2 frame. One CPCS packet may be sent over two frames, but one CPCS packet shall contain data corresponding to 2 ms user data traffic.

[0051] The encapsulation of the MPEG2 TS according to the invention is shown by the diagram of FIG. 3.

[0052] At the receiving side, source packets are recovered by processing the CPCS length field and discarding the padding bytes. Source packets are then buffered by processing the SSCS ‘wireless’ time stamps so that packets are transmitted with a constant delay. IEC 61883 part 4 mechanisms are still valid, except that the HL2 bus jitter (5ms) is different from the IEEE 1394 bus jitter (311 μs). The buffer size has to be adjusted accordingly.

[0053] Isochronous resource reservation will now be described:

[0054] It is supposed in this section that the wireless part of the network comprises an Isochronous Resource Manager (this may typically be the Central Controller) whose task it is to attribute channels and bandwidth to requesting wireless devices.

[0055] When an application reserves resources for an isochronous stream, it sends a lock request to the lsochronous Resource Manager (‘IRM’) of the wireless link, asking for a dedicated channel.

[0056] A format of the lock request message is illustrated by FIG. 4.

[0057] According to the present embodiment, it is proposed to use some of the reserved bits of the format of FIG. 4 to indicate what kind of SSCS encapsulation is requested, as illustrated by FIG. 5. The value of this new ‘streamType’ field should be as indicated in Table 1: TABLE 1 Value Status 0x00 Reserved 0x01 Asynchronous stream 0x02 Isochronous stream (isochronous packets encapsulation) 0x03 Isochronous stream (MPEG2 TS encapsulation according to the present embodiment) Other Reserved

[0058] When an application sends a lock request asking for an MPEG2 TS ‘native’ encapsulation according to the invention, the Central Controller may have to check whether this mode is supported, if this mode is only an option. If it is supported, the Central Controller issues a corresponding message to the device having made the lock request, otherwise the isochronous packets encapsulation is used.

[0059] According to the present embodiment, the encapsulation scheme which has been selected is indicated in the DLC_MULTICAST_SETUP message in a dedicated Information Element (‘IE’), as part of the Convergence Layer container. This message is sent to all devices of a given multicast group.

[0060] This IE is illustrated by FIG. 6. Table 2 indicates the signification of each item in this Information Element: TABLE 2 Value Status 0x00 Reserved 0x01 Asynchronous stream 0x02 Isochronous stream (isochronous packets encapsulation) 0x03 Isochronous stream (MPEG2 TS encapsulation according to the present embodiment Other Reserved

[0061] This allows any wireless device's SSCS to be informed of the selected encapsulation mode when a DLC multicast connection is set up.

[0062] Two cases have been considered here: the transmission mode according to the present embodiment may be mandatory, or may just be an optional feature.

[0063] In case of mandatory support, every HL2 wireless device implementing an IEEE 1394 SSCS shall implement this encapsulation mode. When MPEG2 data is transmitted over HL2, this encapsulation mode shall be used.

[0064] According to the present embodiment, the oPCR format described in the already cited application is used to reflect how much bandwidth is required to transmit data in this native MPEG2 encapsulation mode.

[0065] In case the encapsulation method according to the invention is only optional, there may be devices that support this encapsulation mode, while others will not. According to the embodiment, a mechanism allowing negotiation of an encapsulation method is implemented, as will now be described:

[0066] The capability negotiation during the association phase of a wireless device is carried out as follows.

[0067] During the association, a wireless device sends its ‘EUI64’ identifier (which is a fixed identifier unique to this device) to the Central Controller in an Information Element within a ‘RLC_INFO’ message. Another Information Element has to be defined so that the SSCS capabilities can be described (at least whether the SSCS supports the native MPEG2 TS mode or not). This Convergence Layer capability Information Element can be sent in the same RLC_INFO message as the EUI64 Information Element.

[0068] An example of such an Information Element is illustrated by FIG. 7.

[0069] In this Information Element, a set MPEG2 TS Cap flag means that the SSCS of the wireless device being associated supports the native MPEG2 mode. Otherwise it only supports the isochronous packet mode.

[0070] The Central Controller maintains a database of the capability of each associated device.

[0071] In addition to the association process, the resource reservation mechanism also has to deal with this optional feature.

[0072] When an application of a wireless device sends a lock request to the Central Controller asking for a MPEG2 TS native encapsulation, the Central Controller has to check whether this mode is supported. If it is supported, it is used, otherwise the Isochronous packet encapsulation is used.

[0073] The selected encapsulation scheme is indicated by the Central Controller in the DLC_MULTICAST_SETUP message in a dedicated (and previously described) Information Element, as part of the Convergence Layer container.

[0074] When a wireless device implements the native MPEG2 encapsulation and an OPCR, it uses the native MPEG2 encapsulation scheme to express bandwidth requirements in the oPCR: this means that the oPCR payload field shall contain the number of source packet quadlets within one HL2 frame. The overheadID field shall reflect the CPCS overhead within one frame.

[0075] If an application makes a reservation, it shall use the OPCR values (payload and overheadlD of the source oPCR). The Central Controller then is able to finally decide which encapsulation scheme has to be used (depending on source and sink capabilities), and is also able to make the appropriate calculation if needed (if the native MPEG2 encapsulation cannot be selected because the sink device is not capable), then the isochronous packet encapsulation will be selected, and the Central Controller is able to know (based on IEC 61883 part 4) rules how many isochronous packets will be built and what will be the total amount of data (one packet every 125 μs cycle including a CIP header and a isochronous packet header put into one CPCS packet). The gain in efficiency of this method resides in minimizing the padding. When one wireless packet is built, a padding is added so that the wireless packet is an integer number of 48 bytes. If a wireless packet contained only one isochronous packet, a padding would be added to every 1394 isochronous packet. With the present method, a wireless packet contains several 1394 isochronous packet payloads, and is generated every HL2 frame. Thus padding is generated only every HL2 frame (2ms) and not every 1394 cycle (125 μs). 

1. Method for isochronous data packet transport over a wireless network, comprising the steps of: collecting a plurality of isochronous data packets at a service specific convergence sublayer (SSCS) of a wireless source device; posting said plurality of isochronous data packets as a whole to a common part convergence sub-layer (CPCS) of the wireless source device, wherein said plurality of isochronous data packets posted to the common part convergence sub-layer corresponds to the amount of isochronous data packets generated by a transmitter over a wireless frame period.
 2. Method according to claim 1, further comprising the step of adding error protection redundancy data to each isochronous data source packet at the service specific convergence sublayer.
 3. Method according to one of the claims 1 or 2, wherein the isochronous data packets are MPEG 2 TS packets, said MPEG 2 TS packets being posted unsegmented to the common part convergence sublayer. 